Hi lukaspovilonis, thanks for bringing these issues to our attention.
For #4, do you have the same REST data source(s) set up in both orgs with the same name(s)? Deploying the pages to the org doesn’t affect the data sources, you need to configure these separately.
For #1-3, the team is looking into these questions and will respond when we have more insight.
Here are a few updates:
- Longer XML get cut off when I pull ( I can see that lines are missing), but original file has roughly 14k lines of XML, squished into roughly 8k lines.
For this one, is Skuid actually stripping out content from the original file (e.g. specific lines of XML or JS code), or just compressing things like JS code? Skuid compresses JS code when this operation happens, but doesn’t actually REMOVE any content from the page (i.e. the page should function the same if you copied/pasted that XML back into your Salesforce org).
- Longer XML get also cut off when I push (i can see that lines are missing).
This has been logged as a known issue in our tracking system. There is not a target date for getting this issue addressed yet but our devs are aware of it. We will let you know when the fix is available.
- When pulling, XML of SKUID page gets messed up or at least JS Snippets. I noticed that JS Snippets gets squished into one line and that probably messes up syntax somehow. (Not always, but) most of the time I get an unexpected token error message.
As mentioned under #1, Skuid SFDX does compress JS. In general, this should NOT break the snippets in runtime. Are you getting the unexpected token error message in the App Composer or runtime? If you don’t mind sharing your page XML as an attachment, that would be helpful here.
- After pulling a SKUID page from an org, and pushing it into another Org, I get error messages related to REST models.
Do you have the same REST data source(s) set up in both orgs with the same name(s)? Deploying the pages to the org doesn’t affect the data sources, you need to configure these separately.
@lukaspovilonis , good news! A few of the issues you reported have been fixed, and are available in our latest version of skuid-sfdx: https://github.com/skuid/skuid-sfdx/releases/tag/0.4.0
The specific issues resolved that you reported are:
Longer XML get also cut off when I push (i can see that lines are missing).
When pulling, XML of SKUID page gets messed up or at least JS Snippets. I noticed that JS Snippets gets squished into one line and that probably messes up syntax somehow. (Not always, but) most of the time I get an unexpected token error message.
I believe it’s possible that #1 from your original post is actually related to #2, so that may be resolved as well. You will have to test the update to verify.
To update to the latest version, run sfdx plugins:update on your machine. Once that’s done, you can run sfdx plugins to view the list of plugins, and make sure skuid-sfdx is now on 0.4.0.
If you have any problems with the update, please let us know! Hope that resolves your issues.
Emily
- Sorry, I was not able to re-produce the issue that I originally had, most likely I made a mistake on my end.
- Thank you.
- I get the error in runtime, the page doesn't load (I assume it calls an inline function onload) and I get an error called "Uncaught SyntaxError: Unexpected token ')'", in other pages it's a "." instead of ")". I have email a Rob Hatch (regarding Skuid CLI) with a file of original XML (before the page is pulled with sfdx) that produces this and 2. error. Would you be able to get the file from Rob? To recreate, create a page in composer, paste XML, pull with sfdx and paste the pulled XML with sfdx back into composer.
- Most likely that was the issue, thank you for the suggestion.
Thank you very much for the effort you’re putting in and looking forward to the updates.
Thank you Emily for the update. I got it installed and running. I’m definitely not hitting any errors that I did before. I will be back if I encounter any errors.
For future, should I post any troubles I encounter on Skuid Community or Skuid sfdx Github?
Thank you.
@lukaspovilonis For now, I’d say either place is fine. We’re currently still working through the best way to manage requests around skuid-sfdx, but we are doing our best to monitor both channels.
Thanks, Emily