Creating a release build in vue-cli-template (old)
First clean the dist folder before building either an android or ios build:
npm run clean
import { Application, CSSUtils } from '@nativescript/core'; | |
function toggleGlobalClass(className: string) { | |
const rootView = Application.getRootView(); | |
const enabled = rootView.cssClasses.has(className); | |
if (enabled) { | |
CSSUtils.removeSystemCssClass(className); | |
rootView.cssClasses.delete(className); | |
// also remove from all modals |
<Frame @loaded="onFrameLoaded" /> | |
<!-- and in all the <Page> elements --> | |
<Page path="/path-of-this-page">...</Page> | |
<script> | |
export default { | |
data() { | |
return { |
methods: { | |
beforeEnter(el) { | |
el.setAttribute('translateY', -200); | |
}, | |
enter(el, done) { | |
el.nativeView | |
.animate({ | |
translate: { | |
x: 0, | |
y: 0, |
// at the top of webpack.config.js: | |
const nodeModulesPath = path.resolve(__dirname, 'node_modules') | |
externals: (context, request, callback) => { | |
if(context.startsWith(nodeModulesPath)) { | |
const module = context.replace(nodeModulesPath, '').split(path.sep).find(p => !!p) | |
try { | |
const pkg = require(path.resolve(nodeModulesPath, module, 'package.json')) | |
#Repositories vs No Repositories
I always thought decoupling is a good thing but there are cases where you think you are decoupling when in fact, you are just adding a new layer to the coupled code.
Let's see an example, say you have a typical CRUD application, a blog (simple example, applies even more to more complex cases). You have Posts, Categories, and Tags let's say. With eloquent it's pretty easy to set the relations up and use them.
You want to be proficient with your code, and you create a PostRepository interface and others (Tag / Category). Then you proceed to create an concrete implementation for Eloquent, and you just "map" those common methods to eloquent.