use pagename as a namespace for javascript and models

Pat VachonPat Vachon πŸ’ŽπŸ’ŽπŸ’Ž
edited June 25, 2020 in Ideas
To keep things from getting improperly referenced between pages via page includes.



2
2 votes

Under Consideration Β· Last Updated

Comments

  • Rob HatchRob Hatch πŸ’ŽπŸ’ŽπŸ’Ž
    edited September 1, 2016
    Interesting thinking. Β We do know there are occasional troubles when you rename models... Β  We also really should solve for model uniqueness accross pages. Β Its complicated stuff, but considering the number of times that theme emerges in the forum, Β the need is certainly out there.Β 
  • Pat VachonPat Vachon πŸ’ŽπŸ’ŽπŸ’Ž
    edited June 25, 2020
    Just remembering this post when writing up some best practices. Is this still under consideration?
  • Pat VachonPat Vachon πŸ’ŽπŸ’ŽπŸ’Ž
    edited June 25, 2020
    With my push to simplify my org, I'm noticing this issue again. Is this under consideration or planned?

    My use case for this is leveraging the Page Include component for almost all pages. This, in certain instances cause the same page include to be on the same page twice, which causes an issue. Wouldn't be an issue if Models had a namespace. Or that very least enable models to respect and their components to respect the "_parentPageId" property.
  • Matt SonesMatt Sones πŸ’ŽπŸ’ŽπŸ’Ž
    edited June 25, 2020
    The need to include the same page in more than one location on a complex page has come up several times. I've found myself cloning pages to give them unique names (and updating all the model names) just so I can include the same content in two different places...

    which is just silly.
  • Pat VachonPat Vachon πŸ’ŽπŸ’ŽπŸ’Ž
    edited May 31, 2017
    Yup. Agreed. At least I'm not the only one.
  • Matt SonesMatt Sones πŸ’ŽπŸ’ŽπŸ’Ž
    edited May 31, 2017
    You're not alone!
  • Matt SonesMatt Sones πŸ’ŽπŸ’ŽπŸ’Ž
    edited May 31, 2017
    Not only is it silly, it's contrary to the skuid vibe.
  • Pat VachonPat Vachon πŸ’ŽπŸ’ŽπŸ’Ž
    edited June 25, 2020
    Exactly. I want to leverage all pages, models and components as much as possible. I'm even considering making a detail page controller using js inline to max out how it's used. View, New, Clone, and Edit. As well as taking in a adoptive row so as to not need to query for it. All about uber fast UX.
  • Pat VachonPat Vachon πŸ’ŽπŸ’ŽπŸ’Ž
    edited June 25, 2020
    Please tell me this is going to happen.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!