Yes, I am trying to create one private repo with all of my element definitions.
I think the crux of it is that each of my elements is in a child directory of my private/shared elements project (call it 'all_my_elements'). I have added 'all_my_elements' as a dependency to my designer project's bower.json. I have added 'components/all_my_elements/metadata.html' to the metadata array. It contains a link to a metadata file for each of my elements. The problem is, that the element definitions themselves are not found by the designer, seemingly because the source of the element is in 'components/all_my_elements/my_example_element' and not 'components/my_example_element'. If I copy 'components/all_my_elements/my_example_element' to 'components/my_example_element', the designer finds the element and shows it in the palette with the correct metadata. A hack I found was to add my_example_element as a file-pointer dependency to the bower.json of all_my_elements. It kinda worked but messed up the tests in all_my_elements, so is not a practical solution. I hope that makes sense. Let me know if you need to see some code. It's a bit cumbersome to post because it's spread across two repositories. On Tuesday, July 22, 2014 7:52:33 PM UTC+2, Rob Dodson wrote: > > Would it be possible for you to create one private repo that contains all > of your element definitions? Have you tried that and run up against a > problem? > > > On Tue, Jul 22, 2014 at 9:41 AM, Keith Garrod <[email protected] > <javascript:>> wrote: > >> I am trying to create a collection of elements that can be shared between >> multiple private projects. >> >> I want to include testing (polymer-test-tools) and to use my own >> components in Polymer designer. I am finding it challenging to set up a >> directory structure which supports private/shared elements and is >> consistent with the existing toolset. >> >> The tooling seems to be geared towards creating a repository for each >> element. That's all very well for public elements, but not so great for >> private/shared >> elements. My private/shared collection will easily exceed 50 elements >> (github large plan). Apart from anything else, that's $1/month/element, >> which seems like a lot for hosting a few lines of code! >> >> I do understand that the tooling is nascent, but I am wildly excited >> about the potential of Polymer for my project and would really appreciate >> any pointers . >> >> Follow Polymer on Google+: plus.google.com/107187849809354688692 >> --- >> You received this message because you are subscribed to the Google Groups >> "Polymer" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/polymer-dev/d49637dc-5775-4f6e-a2a4-d1b53123c3ee%40googlegroups.com >> >> <https://groups.google.com/d/msgid/polymer-dev/d49637dc-5775-4f6e-a2a4-d1b53123c3ee%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/4878279c-dbcd-4dc9-8074-ace42232578f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
