balderdashy / balderdashy/sails

sails 1.0 sails.controllers

Open
#4,672 3 comments 0 reactions 0 assignees View on GitHub
docs does this answer your question?
Dominant language
JavaScript
Stars
22.8k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

Hi,

A lot of hooks used to add controllers using sails.controllers, since sails 1.0 that functionality is broken...
and a lot of useful dependencies do not work any more, I really am very disappointed in the sails team, so many useful dependencies stop working after each update, it is hard to work with this framework this way...

I tried using the sails-auth-new dependency and it doesn't work with sails 1.0 because it attempts to register its controllers which causes:

> warn: Ignored attempt to bind route (/logout) to unknown action { controller: 'AuthController',
> skipAssets: true,
> action: 'logout' }

I am going to fork this dependency and try and fix it,
how can i register a controller?

Contributor guide

Open the contributing guide

Research direction

Start with sails-auth-new's attempt to register AuthController under Sails 1.0, focusing on the ignored /logout route and its unknown-action warning. Determine the supported controller-registration path and verify that the dependency's logout action can bind successfully without the warning.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.