merkle-open / nitronetsitecore Goto Github PK

Nitro itself would adopt schema.json definitions on all patterns. That's a good opportunity to auto-generate C# model classes based on their schema.json contract to reduce more "boring and stupid activities" and speed-up the backend-implementation time significant.

More Informations, see:

• http://json-schema.org/
• https://github.com/namics/generator-nitro/blob/feature/pattern-abstraction/generators/app/templates/patterns/molecules/example/schema.json

• Add support for Sitecore 9.0
• Sitecore 8.1 and Sitecore 8.2 are still supported
• Add documentation for using NitroNet for Sitecore with Sitecore 9.0
  • Helix support?

Hello,

I have followed the steps for NitroNet sitecore Setup.

The issue that I'm facing is that it is not working for Html file for the main layout and I'm getting an Internal Server Error message.

When for testing purpose I have added a cshtml file the error got removed but in case of cshtml file it is considering the handlebars as normal text.

It would be great If we can get a sample solution for NitroNetSitecore

NitroNet.Sitecore is using the dynamic placeholder implementation in every case. This is not really necessary on top level of a page or if a component is unique on a page.

Please add the possibility to enforce the standard Sitecore placeholder with an attribute on the placeholder-helper of the Sitecore NitroNet integration.

Actually it's necessary to have *.html Files to use a template for Sitecore Layouts. Please provide additional file extensions such as *.hbs or *.hb

Can I use NitroNetSitecore for a view rendering where I want to pass a sitecore model or using glassmapper ?

Please provide a demo solution to test and play very fast with this framework.

Perhaps it's possible to change the ViewEngine of Sitecore Habitat and implement NitroNet into this public demo project.

The NitroNet.Sitecore.Microsoft.DependencyInjection IoC container has no service implementation of Sitecore.Database. It's important to avoid the usage of Context.Database (or the Factory-Way) directly in a controller. Let us make NitroNet.Sitecore solutions as maintainable as possible.

The view engine can be registered in Sitecore's initialize pipeline. Currently, this is a manual step which can be done by the NuGet package automatically.

I'm able to render my component in sitecore, but I'm unable to edit the component in field level.

I am trying to use Edit Frame as mentioned in the provided document, but somehow it is not much clear to me.

Currently Whole component can be selected. but I want to edit individual fields in exp editor.

Show some internal informations of the renderings usage of NitroNet as a /sitecore/admin/-Page. E.g.:

• List all cached templates
• List all cached components
• Input view string and check if valid

Sitecore 9.0.1 ships with new renderings for EXM (e.g. "Footer" or "Header"). Chances are that projects want to create rendering with the same name and run into this exception. We might want to add the possibility to ignore certain rendering paths (e.g. config setting).

Addition: It would be helpful to enrich the exception message with information of which renderings are duplicates. Catch exception and rethrow.

Exception:

Error Rendering View: /Views/Shared/NitroLayout.cshtml: Error while rendering view: '/Views/Shared/NitroLayout.cshtml' (model: 'Sitecore.Mvc.Presentation.RenderingModel, Sitecore.Mvc').
at Sitecore.Mvc.Presentation.ViewRenderer.Render(TextWriter writer)
at Sitecore.Mvc.Pipelines.Response.RenderRendering.ExecuteRenderer.Render(Renderer renderer, TextWriter writer, RenderRenderingArgs args)
Inner Exception: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add) at NitroNet.Sitecore.Rendering.SitecoreRenderingRepository.GetAllRenderings() at NitroNet.Sitecore.Rendering.SitecoreRenderingRepository.GetRenderingId(String renderingName) at NitroNet.Sitecore.SitecoreMvcNitroTemplateHandler.RenderComponent(RenderingParameter component, RenderingParameter skin, RenderingParameter dataVariation, Object model, RenderingContext context) at NitroNet.ViewEngine.TemplateHandler.ComponentHelperHandler.Evaluate(Object model, RenderingContext context, IDictionary2 parameters)
at lambda_method(Closure , RenderingContext , Object )
at NitroNet.ViewEngine.ViewEngines.VeilViewEngine.VeilView1.Render(T model, RenderingContext context) at NitroNet.ViewEngine.ViewEngines.VeilViewEngine.VeilViewAdapter1.Render(Object model, RenderingContext context)
at NitroNet.Sitecore.SitecoreNitroNetViewEngine.SitecoreViewAdapter.Render(Object model, RenderingContext context)
at System.Web.Mvc.Html.PartialExtensions.Partial(HtmlHelper htmlHelper, String partialViewName, Object model, ViewDataDictionary viewData)
at Sitecore.Mvc.Presentation.ViewRenderer.Render(TextWriter writer)

I wonder why the setting is used in the nuget package, but is not mentioned in the source here at all. And then - why the features folder is excluded by default.
Does not make any sense for me - but I'm probably missing something here ;)