How do I test a YAML form for problem reporting on a GitHub project page before I install it? - github

I'm a Git/GitHub beginner and don't know YAML (yet).
I found this about making an issue reporting form, but I'm sure I won't get it right the first try, so I need a way to run it as a test without inflicting it on the live project.
I searched briefly and didn't see any application that would open and render YAML the way I would use a browser for HTML.
What's the best way to approach this?

I'd normally create a new project or repo to test on and when happy, simply copy paste the final result to the project you want to have these enabled for real.

Related

Xcode Build Fails on Archive, but the Build does not Fail on Run with ResearchKit

What I am trying to achieve is to archive the app and still have a working consent form on the app.
Although this piece of code is deprecated and says to use ORKInstructionStep I haven't found anywhere how to use ORKInstructionStep instead of ORKVisualConsentStep.
Whenever I try to Archive the app I keep getting this problem. Still, I also can't remove the ORKVisualConsentStep because I haven't been able to find anywhere how to add the consentDocument otherwise.
I've looked at so many other tutorials and all of them use the ORKVisualConsentStep and haven't seen anyone that has had this problem show how to still keep the consent form working. I can get the app running on a phone but I can't get it to archive so not entirely sure what is going on.
Any insight would be beneficial thank you
If you don't know how to added all frameworks, libraries and Embedded contents then you can find shown below what I shared and you can remove it. Please check after your local files remove it.
I managed to fix the problem by using cocoapods to install the ResearchKit framework instead of dragging ResearchKit into my project. It now archives however I had to comment out this line of code instructionStep.imageContentMode = .scaleAspectFit for my survey tasks.

Deploying solution with mulitple windows forms projects

I apologize if this has been answered in another post, I can't seem to find it if it has. Anyway, I have built a back end utility for a fellow streamer friend of mine but I can't seem to figure out what I'm doing wrong when it comes to deploying it. This is a project that will be expanded on in the future, and possibly have more windows form projects. So here is what I am running into (With Pictures):
Here is my solution explorer with the projects:
When I go to build the deployment I've tried making all the projects "outputs" and got this error. Thinking it was there were too many Project Outputs I changed it to where the startup project would be the output and the others would be either source or content files. Still got these errors. Here is the File System Setup:
And when I go to run the build to create the deployment, here are the errors I receive:
I don't know/don't see what I am doing wrong here and would very much appreciate a point in the right direction. Thank you all so much in advance.
Check your updates. I remember there is an option to review or check the status of latest updates.
I found this article about that issue but it looks like a general error with updates or the installation
It is not too long but maybe it does not help. I hope it helps, good luck

When using Ember-cli-blanket for coverage data includes files from Ember itself instead of only files I created

I added ember-cli-blanket into my project and managed to get it working fine. localhost:4200/tests?coverage would show the coverage data. However it included files such as 'project/components/modal-dialog' or 'project/components/modal-dialog-overlay' in the results, which are not files in the project, but are included by Ember since the project uses a modal dialog in one of the template files. These extra test files don't give me anything new since I'm not testing the ember codebase and actually muddle the results by mixing in my tests with other ones. The project is still small, and with ~11 actual files needing testing, there were around 12 files I had to add to the loaderExclusions in blanket-options.js. Some could be gotten rid of with an exclusion like:
loaderExclusions: ['project/initializers'],
But for the ones under project/components, I do want to test the components that are part of the project, so I had to exclude each one individually. And there's no guarantee that excluding all initializers files won't come back to bite me if I actually end up with any files in there I want to test. Considering how small the project is so far, and the fact that there are more exclusions than actual files, this doesn't seem like a sustainable solution.
Am I doing something wrong in my set-up? Is this something I can solve with my filter which is currently on a default of:
filter: '/.*project/.*/',
Any help would be appreciated.
As a sidenote, I've been looking into testem with Istanbul as well as Karma as other options for coverage data in Ember but have been unable to get anywhere with them. If you have suggestions on the setup for those that would also be fine.
It doesn't look like there's anything wrong with your setup. What you're seeing is apparently due to how blanket.js works. See this issue for more information: https://github.com/sglanzer/ember-cli-blanket/issues/17
I was using ember-cli-blanket then found ember-cli-code-coverage. As of this writing, the sandersky fork, at 9f1dd33f, works great for me to solve the type of problem you're describing.
https://github.com/kategengler/ember-cli-code-coverage/pull/11
It solves it not using blanket, but using istanbul.

Accidentally published CompositeC1 with precompile on

I accidentally published Composite C1 from Visual Studio with "Precompile during publishing" when I first set it up and have now come to realize that several plugins do not work with precompile turned on. Unfortunately I have no idea how to reverse this. I've tried several things to no avail. I usually end up with a 500.0 error. If I go to the admin interface everything is working properly, and I can even preview the pages, but from the customer side all I get is a 500.0 error.
Of course I could republish from the Visual Studio project I have, but that project has the default template on it. I've tried copying what appears to be changed on the server to the original project but I end up with a 500 error. I've tried removing all the precompiled stuff on the server but I end up with a 500 error. I'm pretty lost.
At this point I'm willing to do anything. Is there a doc explaining how to copy the content to a newly downloaded copy, kind of like an upgrade doc but "side-grading"? I am using the most current version at the time of writing this 4.2 Update 1
Thank you
Solved use the PackageCreator suggested by wysocki's answer. It was not exactly straight forward to create the package. The errors can very cryptic at times. So here are some of the issues I encountered and how I got past them:
wysocki was correct to suggesting starting with a bare bones installation even though my original project was started with the Venus theme. I tried both ways.
I encountered issues with the MasterLayout and the Page Template Features which are currently not supported by the PackageCreator, although they may be supported in future versions. The solution was to add the missing elements to the fresh C1 project from the original C1 installation in the App_Data/PageTemplates and App_Data/PageTemplateFeatures folders.
A few times I ran into an issue where I added the same page or function twice to the PackageCreator. This was obviously my fault, but it should be mentioned that you can add the same site element twice which throws and error on import. Make sure you are careful to only getting one of each when creating the package to be exported.
If you are getting and error and it uses and Id like "4061397b-ee9e-4512-984d-f2b2d41eb654" I've found that it was very helpful to extract the zip file you are trying to import and then search the extracted folders for that Id. The lines with the Id usually have more information on them that will help you to identify exactly what content page or whatever the error is being generated from.
If you are using installed packages in your project like SimpleSearch for example, make sure you don't add it's functions to the PackageCreator. Install them separately.
I had an issue where I somehow had an element in the Data section that didn't have a "type". The error simply "The type cannot be empty". This was obviously tough to find so I suppose the lesson is, less is more. If you think your project might have a few elements that are unnecessary, don't add them at first and see if the project you import them into complains about missing them. It's much easier to troubleshoot missing elements than it is to figure out which element is causing the issue that you really didn't need.
Is there a doc explaining how to copy the content to a newly downloaded copy
You can try and export content / templates / anything else related to a "package" via Composite.Tools.PackageCreator.
Its latest version gives you quite a lot of flexibility in what you can export ("package") - please its user manual.
Once the package is made and downloaded, you can go on and install it on a new website. If you export / import a lot of content / templates etc, it makes sense to have a "Bare Bones" site as the new one.
All the starter sites like "Neptune", "Venus" are installed as a bunch of packages in specific order during Composite C1's initial setup.

Import .apk file into Eclipse

I'm trying to open various .apk files in Eclipse for the purpose of viewing the source code. I'm developing for Google Glass, and I need to see how the code of the third party software I downloaded is executed. I'm able to view the code using JD-GUI and dex2jar, but I can't compile and run it on Glass. Whenever I try to import the existing code in Eclipse, it is grayed out and I can't select it: even the Google made samples like the compass and charades apps. I am new to this, so perhaps I've missed a step or something of the sort. I'd greatly appreciate any help or advice on the matter!
Thanks, Jordan
Generally you don't access the source code via the jar/apk. Those are compiled, or translated, from the source code to the code that Glass/Android actually runs. Because of this, you're probably not going to be able to view the actual source code for these projects.
If you want to get the source code (and import it into Eclipse) for the Google Projects, go to https://github.com/googleglass/?query=gdk, select one of the applications, and click the "Download ZIP" button. This will give you a .zip of the source code.
If you're feeling really brave and want to learn even more, try cloning the repository with git. The git website has a great tutorial/introduction at http://git-scm.com/book/en/Getting-Started-Git-Basics.